Server consolidation using virtual machine resource tradeoffs

ABSTRACT

Server consolidation using virtual machine resource tradeoffs, is provided. One implementation involves assigning a virtual machine to a target physical server based on a plurality of virtualization parameters for maximizing utility of a plurality of virtual machines and physical servers. The assigning performs resource allocation for the virtual machine based on capabilities of the target physical server and a plurality of virtual machine resource requirements. Virtualization parameters include a reservation parameter (min) representing a minimum resources required for a VM, a limit parameter (max) representing a maximum resources allowable for the VM, and a weight parameter (shares) representing a share of spare resources for the VM.

BACKGROUND

1. Field of the Invention

The present invention relates generally to server consolidation. In particular, the present invention relates to consolidation of servers to a virtualized server environment using virtual machine resource tradeoffs.

2. Background of the Invention

Server virtualization involves simulating several virtual machines (VMs), each running a separate operating system (OS) instance on a single physical server. Each OS may run in a different VM. For example, Xen is a virtual machine monitor (VMM), also known as a hypervisor, for managing the VMs that execute on a host operating system to provide the functionality of several guest operating systems on top of the host, on the same computer hardware (physical machine), at the same time. Server virtualization technologies are becoming increasingly commonplace in data centers. These enable applications to be packaged inside virtual machines and allow multiple VMs to run on a single physical machine without interfering with each other. This provides increased utilization of resources and consolidation of server, space and data center costs.

Modern server virtualization technologies are transforming enterprise data centers including information technology (IT) hardware and software systems. By consolidating multiple physical bare-metal servers into fewer virtualized machines, enterprises are improving resource utilizations and reducing operational costs. Virtualization technologies provide administrators with the ability to manually set virtualization parameters. The virtualization parameters include a minimum amount of resource required for a VM (min, also referred to as a reservation), a maximum allowable resource (max, also called a limit) and its share of spare resource (shares, also referred as the weight in Xen schedulers).

BRIEF SUMMARY

Server consolidation using virtual machine resource tradeoffs, is provided. One embodiment involves assigning a virtual machine to a target physical server based on a plurality of virtualization parameters for maximizing utility of a plurality of virtual machines and physical servers. The assigning performs resource allocation for the virtual machine based on capabilities of the target physical server and a plurality of virtual machine resource requirements.

Maximizing utility of the plurality of virtual machines and physical servers may comprise a tradeoff between minimizing a number of physical servers utilized, minimizing power consumption, and maximizing utilization and performance.

The assigning may further comprise obtaining the plurality of virtualization parameters for the virtual machine. The virtualization parameters may comprise: a reservation parameter (min) representing a minimum resources required for a virtual machine, a limit parameter (max) representing a maximum resources allowable for a virtual machine, and a weight parameter (shares) representing a share of spare resources for a virtual machine.

The assigning may further comprise performing a power-performance tradeoff based on the plurality of virtualization parameters to determine an assignment of the virtual machine to the target physical server for maximizing utility of the plurality of virtual machines.

The assigning may further comprise discounting a power cost incurred, and considering an amount of resources on the target physical server to be allocated to the virtual machine.

The resource allocation may further comprise determining utility of the virtual machine based on at least one of: value and output the virtual machine can generate based on a plurality of resources allocated to the virtual machine. The resource allocation may further comprise adjusting an amount of resources allocated to the virtual machine based on a plurality of available resources, a power consumption cost, and utility of the virtual machine. Consolidating may further comprise decommissioning a plurality of physical servers and deploying a plurality of virtual machines.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows architecture of an embodiment of a virtual machine system;

FIG. 2 shows an example of plural virtual machines for consolidation onto multiple servers;

FIG. 3 shows an example of server consolidation using virtual machine shares and power-performance tradeoffs;

FIG. 4 shows a flowchart of an example process for server consolidation using virtual machine shares and power-performance tradeoffs;

FIG. 5A illustrates example steps for server consolidation using virtual machine shares and power-performance tradeoffs;

FIG. 5B shows a plot of allocated resource vs. utility based on service level agreement (SLA) information;

FIG. 6 shows an example system for server consolidation using virtual machine shares and power-performance tradeoffs;

FIG. 7 shows a block diagram of a system in which a process for server consolidation using virtual machine shares and power-performance tradeoffs may be implemented.

DETAILED DESCRIPTION

The following description is made for the purpose of illustrating the general principles of the invention and is not meant to limit the inventive concepts claimed herein. Further, particular features described herein can be used in combination with other described features in each of the various possible combinations and permutations. Unless otherwise specifically defined herein, all terms are to be given their broadest possible interpretation including meanings implied from the specification as well as meanings understood by those skilled in the art and/or as defined in dictionaries, treatises, etc. The description may disclose several preferred embodiments for information technology (IT) virtual machines. While the following description will be described in terms of such languages for clarity and placing the invention in context, it should be kept in mind that the teachings herein may have broad application to all types of systems, devices and applications.

Determining virtual machine (VM) shares and power-performance tradeoffs during server consolidation, is provided. Consolidation herein involves a process of transitioning applications from non-virtualized physical servers (e.g., Windows server, Linux servers) to fewer virtualized servers (e.g., VMware, Xen) by converting them into VMs.

A consolidation process disclosed herein assigns VMs to physical server and utilizes virtualization parameters such as minimum (min) amount of resource required for each VM and maximum allowable resource (max) for the VM, to determine share of spare resource for each VM application. Such virtualization parameters are useful constructs that ensure intelligent distribution of resources between different applications (especially when there are a heterogeneous set of VM applications with different priorities and resource affinities). The consolidation process is directed to placement of VMs in terms of which combinations of application VMs are placed on each physical server, while considering resource allocation (shares) for each VM based on different priorities and resource affinities. This granularity in resource allocation positively impacts the utility of a consolidated system.

For example, in a typical enterprise data center, there are a variety of co-existing high priority applications such as company e-commerce web server and low priority applications such as an intranet blogging server. According to the consolidation process, in one scenario, under high load situations, valuable processor (CPU) resources are best utilized when allocated to high priority VM applications instead of the low priority ones. Along with different priorities, different VM applications in the data center have a different affinity for each resource. For example, a web server may value additional CPU cycles much more than a storage backup application. In such scenarios as well, CPU resources are best allocated to the higher utility VM application (e.g., the web server).

FIG. 1 shows a functional block diagram of a computing environment 10 that includes hardware resources 11 and software resources 12. The hardware resources 11 include a processor 13, memory 14, and electronic/computing devices 15 (DEV1, DEV2). The software resources 12 includes multiple VMs 16 (VM1, . . . , VMn) that are managed by a virtual machine monitor (VMM) or hypervisor 17 (e.g., Xen). The hypervisor 17 provides virtualized resources to the individual VMs.

Given a set of applications to be virtualized into virtual machines (VMs), a consolidation process disclosed herein determines proper placement of VM into target physical servers (physical machines (PMs)) based on a power-performance tradeoff during server consolidation, using placement and resource allocation techniques leveraging VM min, max and shares parameters. FIG. 2 shows a set of VMs (e.g., VM1, . . . , VM12) for placement into a set of PMs (e.g., PM1, PM2, PM3).

Virtualization parameters such as min, max and shares for each VM application are automatically determined and utilized in the automated consolidation process disclosed herein. The min parameter represents a resource reservation, the max represents a maximum allowable resource (a limit), and the shares parameter represents share of spare resources (a weight). Setting a min parameter for a VM ensures that it receives at least that amount of resources when powered on, and setting a max parameter for a low priority application ensures that it does not use more resources, thus keeping them available for high-priority applications. Shares parameters provide information to a virtualization scheduler on how to distribute resources between contending VMs. For example, a CPU shares parameter ratio of 1:4 between low and high priority VMs informs the scheduler to provide 4 CPU cycles to the high priority VM for each CPU cycle given to the low priority one.

A suitable placement of VMs onto a small set of target servers according to the consolidation process is determined, and resource allocation for each VM is performed, taking server capabilities into account and taking VM resource requirements into account. The goal is to perform optimization in a manner to essentially maximize total utility of the system, which may be achieved through a suitable combination of minimizing number of servers (PMs) utilized, minimizing power and maximizing utilization or performance. The disclosed optimization aims to maximize the utility gained by the system. Such optimization does not require finding an allocation solution which absolutely minimizes number of physical servers and absolutely minimizes power consumption while simultaneously absolutely maximizing utilization or performance. A utility function takes such measures into account, and finds suitable tradeoff therebetween such that the overall system utility is maximized. The Min, max, shares parameters allow VMs to grow/shrink. Consolidation involves power cost concerns. FIG. 3 shows an example placement of VM1, . . . , VM12 into PM1, PM2, PM3, where PM3 is shut down. Higher-utility solutions with high priority VMs receive more resources.

One embodiment of a server consolidation process disclosed herein comprises implementing power-performance tradeoffs for placement and power consolidation of VMs in data centers, by taking advantage of the min, max and shares features for virtualization technologies. The process allows power-performance tradeoffs in modern data centers running heterogeneous applications, wherein the amount of server resources (e.g., CPU, memory, storage, bandwidth, etc.) allocated to a VM can be adjusted based on available resources, power costs, and application utilities. The consolidation process is applicable across a broad spectrum of inputs (i.e., varying VM sizes and utilities, varying server capacities and varying power costs) thus providing a practical consolidation solution for administrators.

FIG. 4 shows a flowchart of a consolidation process 40, disclosed herein, comprising:

-   -   Block 41: Consider plural VMs to deploy on multiple servers in a         data center.     -   Block 42: Obtain min and max parameters for each VM to be         deployed on a server. Determine shares for each VM (described         further below). The min and max can be obtained manually by an         administrator, or preferably automatically derived from         performance log traces of applications running on physical         servers (PMs). In the latter case, min can be obtained by         observing the absolute minimum amount of resources used by an         application in all its traces (e.g. 512 MHz of CPU). Further,         max can be obtained by observing the absolute max in the traces         and capping it with a configurable threshold (e.g. max         observed=1024 MHz and threshold cap=80%, max value set=0.8×1024         MHz, where “×” represents mathematical product)     -   Block 43: Obtain a utility function for each VM to determine         utility of the VM for resources required by the VM. The utility         function can be obtained manually through the administrator         and/or available as part of an application template provided by         an application vendor.     -   Block 44: Allocate and selectively adjust resources for each VM         based on available resource, a power cost, and an application         utility.     -   Block 45: Employ an allocation function to maximize overall         utility of the VMs minus power costs using the max, min and         shares parameters.

In one implementation, a consolidation process employs VM min, max and share parameters to provide a power-performance tradeoff during the data center consolidation. A set of servers to be consolidated in the data center is considered, wherein the set of servers comprise a set of physical servers and a set of virtual servers.

Employing VM min, max and shares parameters involves obtaining parameters including a reservation quantity parameter, limit quantity parameter, and a weight quantity parameter for each of the VMs for consolidation in the set of servers (PMs). The reservation parameter represents a minimum amount of resources required for the VM. The limit parameter represents the maximum of resources required for the VM. The weight parameter represents a share of spare resources for the VM. Consolidation is based on the reservation, the limit, and the weight parameters for each VM. A utility function is employed for each VM, wherein the utility function considers the output the virtual machine can generate using resources allocated to the VM. The allocated resources for the VM may be adjusted based on available resources, power costs, and application utility.

A set of target VMs, each having a resource capacity, is considered for server consolidation. An allocation function is employed for maximizing the overall utility of the set of VMs, discounting the power costs incurred using the min (reservation), max (limit) and shares (weight) parameters (e.g., using an enhanced knapsack allocation function). Allocation for each VM comprises a target physical machine on which the VM is to be deployed and an amount of resources on the target physical machine to be allocated to the VM. Consolidation may further comprise scenarios of decommissioning physical servers and deploying their applications as VMs.

FIG. 5A illustrates a formal definition of a set of VMs, v={V₁, V₂, . . . , V_(|v|)}, wherein each VM has a <min, max> amount of resource required (i.e., min parameter V_(i).m, and max parameter V_(i).M). Utility functions V_(i).u and V_(i).U corresponds to min and max parameters, respectively. The utility value at V_(i).m is V_(i).u and the utility value at V_(i). M is V_(i). U. A linear interpolation between the two Cartesian points (V_(i).m, V_(i).u) and (V_(i).M, V_(i).U) is determined from application templates and service level agreement (SLA) importance scales. Thus, the utility value at any value x (V_(i).m<V_(i).x<V_(i).M), V_(i).x=V_(i).u+[(V_(i).x−V_(i).m)×(V_(i).U−V_(i).u)/(V_(i).M−V_(i).m)]. In other words, assuming that in a Cartesian coordinate system of allocated resource value vs. utility, a line connects the two points (V_(i).m, V_(i).u) and (V_(i).M, V_(i).U), the utility for allocated resource value x is provided by the value of said line at x, as shown by example in FIG. 5B.

The formalism used in FIG. 5A defines the allocation function to include both assignment and share calculation. The set of VMs is to be consolidated on a set of nodes (servers) S={S₁, S₂, . . . , S_(|s|)}. Each node has a capacity C_(j) of resources, wherein power cost of keeping a server on is P_(j). The goal is to consolidate (pack) VMs into the computing nodes and determine shares for each VM, maximizing total net utility, wherein:

Net Utility=Utility from applications−power cost of keeping servers on.

The consolidation process results in placing VMs among computing nodes in a data center considering a minimum and a maximum range for VM resource requirement along with an associated utility for each VM as a function of the amount of resource allocated to it. In one embodiment of the present invention, the consolidation process comprises: ordering VMs by profitability, order computing nodes by power efficiency and determining VM shares for each VM placed on every computing node, combining VM shares and placement decisions to maximize utility. In one example, an enhanced knapsack strategy may be used to select VMs to pack into servers along with determining the shares for each VM. Example implementations for determining the shares in terms of resource allocation for each VM include: GreedyMax, ExpandMinMax, PowerExpandMinMax and node-based methods, described below.

GreedyMax

The GreedyMax strategy sorts the VMs by their profitability at max, i.e., (utility V_(i).U)/(size(V_(i).M) and places VMs in that order in a first-fit fashion, allocating the max requested resource amount for each VM. A profitability metric captures the utility of a VM per unit resource that is allocated to the VM and is useful in identifying VMs that provide higher utility for every unit of resource that the VM consumes. Sorting the VMs in decreasing order of their profitability enables GreedyMax to perform better than a basic strategy that packs all the VMs at their max requirement and leaves a certain amount of room in each server to account for future growth of the VMs. The GreedyMax performs specially better when the number of server nodes is small.

As shown by example pseudocode in Table 1 below, the GreedyMax process sorts VMs in order of their profitability at max (V_(i).u)/(V_(i).U), and provides resource allocations for VMs at the max. This process always provides an allocation (shares) A comprising max resources to each VM.

TABLE 1 GreedyMax pseudocode GREEDYMAX(VMS

, SERVER NODES

) Output: A :

→

×

⁺  1: ${{Sort}\mspace{14mu} {server}\mspace{14mu} {nodes}\mspace{14mu} {in}\mspace{14mu} {increasing}\mspace{14mu} {order}\mspace{14mu} {of}\mspace{11mu} {power}\mspace{14mu} {rate}},\; \frac{P_{j}}{C_{j}}$  2: ${{Sort}\mspace{14mu} {VMs}{\mspace{11mu} \;}{in}\mspace{14mu} {decreasing}\mspace{14mu} {order}\mspace{14mu} {of}\mspace{14mu} {profitability}\mspace{14mu} {at}\mspace{14mu} \max},{\frac{V_{i} \cdot U}{V_{i} \cdot M}.}$ 3: for i = 1 . . . |

| do 4: Set j ← first node such that Σ_(V) _(i) _(εVSet(S) _(j) ₎A(V_(i)) · Size + V_(i) · M ≦ C_(j) 5: Set A(V_(i)) =

S_(j), V_(i) · M

6: end for 7: return A

GreedyMinMax

The GreedyMinMax process does not always require allocation of resources (shares) to each VM at its maximum requested allocation. It takes into consideration the possibility that some VMs may be more profitable at another smaller size and allocating resources (shares) at that size may yield a better overall utility by leaving room for more VMs. As such, GreedyMinMax involves considering both the min and max points for each VM in determining shares. GreedyMinMax utilizes two items, V_(i) ^(min) and V_(i) ^(max), for each virtual machine V_(i), wherein V_(i) ^(min) is at size V_(i).m and utility V_(i).u whereas V_(i) ^(max) is at size V_(i).M and utility V_(i). U. Beginning with a set |v| of VMs, the GreedyMinMax has a set of 2|v| items v in decreasing order of profitability and starts placing them one by one in a first-fit manner among the available nodes. When placing a V_(i) item, such as corresponding to V_(i) ^(min), GreedyMinMax removes the other one (i.e., V_(i) ^(max)) from the list and vice-versa. This ensures that only one of the two V_(i) items is placed for each VM.

ExpandMinMax (Expanding Between Min and Max)

Instead of selecting the node for each VM in a first-fit fashion, the ExpandMinMax process first computes an estimated utility for each node if the new VM were placed to that node and selects the node that provides the best utility improvement. The utility for each node is computed by first setting a resource allocation for all the VMs assigned to the node to be at min, and then expanding allocation for the VMs that provide the most incremental utility per unit capacity until either the capacity of each is reached, or no further expansion is possible.

A set of VMs Q are feasible for a node S_(j) if the minimum allocation requirements of the VMs in Q sum up to less than the capacity of node S_(j). Once a set of VMs Q is feasible for S_(j), a method of estimating the utility of node S_(j) using the set of VMs Q is applied, such as shown by example in Table 2 below.

Instead of assigning VMs in a first-fit manner, ExpandMinMax assigns each VM to the node S_(j) that maximizes the utility gain (i.e., NodeUtility(S_(j), Set(S_(j))+V_(i))−Nodeutility(S_(j), Set(S_(j)))), wherein Set(S_(j)) is the set of VMs currently assigned to S_(j). If nothing has been assigned to S_(j) yet, Set(S_(j)) is considered to be empty and the corresponding NodeUtility is zero. Note that ExpandMinMax implicitly expands VMs on each node to realize the maximum utility possible from them.

As shown by example pseudocode in Table 2 below, an ExpandMinMax process considers each VM as two items (at min and at max). The process sorts the VMs in order of their profitability (at min and max) based on a utility function, then provides resource allocation (shares) A for a VM on a node only if node utility shows improvement.

TABLE 2 ExpandMinMax pseudocode EXPANDMINMAX(VMS

, SERVER NODES

) Output: A :

→

×

⁺   1: ${{Sort}\mspace{14mu} {server}\mspace{14mu} {nodes}\mspace{14mu} {in}\mspace{14mu} {increasing}\mspace{14mu} {order}\mspace{14mu} {of}\mspace{11mu} {power}\mspace{14mu} {rate}},\; \frac{P_{j}}{C_{j}}$  2:

←   3: for i = 1 . . . |

| do  4: Set item V_(i) ^(min) to be of size V_(i) · m and utility V_(i) · u  5: Set item V_(i) ^(max) to be of size V_(i) · M and utility V_(i) · U  6:

←

∪ {V_(i) ^(min),V_(i) ^(max)}  7: end for  8: Sort

in decreasing order of profitabilities.  9: while

not empty do 10: Remove the first entry of

, say it corresponds to V_(i). 11: j ← argmax_(S) _(j) _(∈S)NodeUtility(S_(j), Set (S_(j)) + V_(i)) − NodeUtility(S_(j), Set(S_(j))) 12: if feasible(S_(j), Set(S_(j)) +V_(i)) then 13: for VMs V_(k) ∈ Set(S_(j)) + V_(i) do 14: Set A(V_(k)) ←

S_(j), x_(k)

where x_(k) is as dictated by the NodeUtility(S_(j),Set(S_(j)) + V_(i)) function 15: end for 16: Remove the corresp. complementary entry of V_(i) from V 17: end if 18: end while 19: return A

Table 3 below shows pseudocode for computing the utility derived from a computing node given the set of VMs that are placed on it.

TABLE 3 NodeUtility pseudocode NODEUTILITY(SERVER S_(j), SET OF VMS Q)  1: remCapacity = C_(j) − Σ_(V) _(i) _(∈Q)V_(i) · m  2: return −1 if(remCapacity < 0)  3: nodeUtility = Σ_(V) _(i) _(∈Q)V_(i)· u   4: ${Sort}\mspace{14mu} {VMs}{\mspace{11mu} \;}{in}\mspace{14mu} Q\mspace{14mu} {in}\mspace{14mu} {decreasing}\mspace{14mu} {order}\mspace{14mu} {of}\mspace{14mu} \frac{{V_{i} \cdot U} - {V_{i} \cdot u}}{{V_{i} \cdot M} - {V_{i} \cdot m}}$  5: for i = 1 . . . |Q| do  6: Let the ith item of Q correspond to VM, V_(i).  7: if (remCapacity > 0) then  8: δ = min(V_(i) · M − V_(i) · m, remCapacity)  9: remCapacity−= δ 10: nodeUtility+= V_(i) · util(V_(i) · m + δ) − V_(i) · u; 11: else 12: return nodeUtility 13: end if 14: end for 15: return nodeUtility The NODE Utility function is used in the ExpandMinMax method described further above and in the PowerExpandMinMax described below.

PowerExpandMinMax

The PowerExpandMinMax process is similar to ExpandMinMax except that PowerExpandMinMax employs a comparative measure comprising the node utility gain minus the proportional power cost incurred (if any) on the new node, for determining shares. The latter quantity applies only when a new node is being started, and in this case the power cost of the machine is scaled down to a size used by the VM and that is considered the proportional power cost for the VM. This may on occasion result in a negative net gain, especially when the proportional power cost of the new node exceeds the utility gain from the VM, in which case the process may select a different (already opened) node that provides better utility gain. However, if all opened nodes yield much smaller (more negative) utility gain, then the new node will still be selected. The latter may occur, for example, if adding a new VM to an already opened node causes more valuable VMs to be compressed.

As shown by example pseudocode in Table 4 below, a PowerExpandMinMax process prevents unnecessary starting of new servers. A VM being added to a node must justify proportional share of power cost. The pseudocode provides resource allocation (shares) A for a VM on a node.

TABLE 4 PowerExpandMinMax pseudocode POWEREXPANDMINMAX(VMS

, SERVERS

) Output: A :

→

×

⁺   1: ${{Sort}\mspace{14mu} {server}\mspace{14mu} {nodes}\mspace{14mu} {by}\mspace{14mu} {increasing}\mspace{14mu} {power}\mspace{14mu} {rate}},\; \left. {\frac{P_{j}}{C_{j}}\mspace{14mu} {and}\mspace{14mu} {set}\mspace{14mu} \overset{\_}{V}}\leftarrow  \right.$  2: for i = 1 . . . |

| do  3: Set item V_(i) ^(min) to be of size V_(i) · m and utility V_(i) · u  4: Set item V_(i) ^(max) to be of size V_(i) · M and utility V_(i) · U  5:

←

∪ {V_(i) ^(min),V_(i) ^(max)}  6: end for  7: Sort

in decreasing order of profitabilities.  8: while |

| not empty do  9: Remove the first entry of

, say it corresponds to V_(i). 10: for (feasible S_(j) ∈ S) do 11: Compute NetGain(S_(j), V_(i)) as given in the formula 12: end for 13: j ← argmax_(feasibleS) _(j) _(∈)

NetGain(S_(j),V_(i)) 14: if feasible(S_(j), Set(S_(j)) + V_(i)) then 15: Assign V_(i) to node S_(j) 16: for VMs V_(k) ∈ Set(S_(j)) + V_(i) do 17: Set A(V_(k)) ←

S_(j), x_(k)

 where x_(k) is as dictated by the Node Utility(S_(j), Set(S_(j)) + V_(i)) function 18: end for 19: Remove the corresp. complementary entry of V_(i) from ! 20: end if 21: end while 22: return A If S_(j) were an already opened node, i.e., Set(S_(j))≠Ø then the net gain NetGain(S_(j), V_(i)) if V_(i) were also added to S_(j) is given by:

NetGain(S _(j) ,V _(i))=NodeUtility(S _(j),Set(S _(j))+V _(i))−NodeUtility(S _(j),Set(S _(j))).

If S_(j) is a new node, then NetGain(S_(j), V_(i)) is given by:

NetGain(S _(j) ,V _(i))=NodeUtility(S _(j) ,{V _(i)})−x _(i) ×P _(j) /C _(j)

where x_(i) is the size allocated for V_(i) on S_(j) as dictated by the NodeUtility(S_(j), {V_(i)}) function.

Node Based Method

Another implementation of the consolidation process comprises: ordering nodes in increasing order of capacity size; for each node, executing an enhanced knapsack strategy to select VMs to pack into the along with determining the shares for each VM; ordering a list of VMs, wherein the list includes two entries for each VM (i.e., profitability at min, profitability at max); traversing the list of VMs; placing each VM into a current node if possible, otherwise moving to the next VM; if an item placed at max, remove its corresponding min; if item placed at min, remove its corresponding max but allow the VM to expand to max later if needed, once the node is closed; when no new VMs at min can fit, close the node, move to the next node; expand any VMs at the closed node in order of highest slope first, until the node capacity is completely filled.

The pseudocode for the above described node based method is shown below:

space_remaining = baseCapacity(n_(i)); Sort VMs: v₁, ..., v_(n) by MAX(profitability_{v_(i),min},profitability_{v_(i),max}), wherein i = 1, .., n; for each VM, if space_remaining > minCapacity(v_(i)), then:     If profitability_{ v_(i),min} > profitability_{ v_(i),max}         Allocate v_(i) to n_(i) at capacity min;     Else         Allocate v_(i) to n_(i) at capacity         MIN(max,space_remaining);     space_remaining = space_remaining − amount_allocated; If space_remaining > 0, then expand VMs allocated at min in order of highest slope first, until space_remaining == 0 or no further VMs are allocated at min.

As such, if the sum of utilities from VMs at their capacities on node n_(i) does not exceed the node-level power cost, then the node is removed from consideration and no further VMs are placed in the system, otherwise the process continues to the next node.

FIG. 6 shows a functional block diagram of a consolidation processing system 60. The system 60 comprises a consolidation processing module 61 in a computer 62, wherein the consolidation processing module 61 implements an embodiment of the consolidation process described herein. The consolidation processing module 61 utilizes VM information from a database 63, to provide information 64 for consolidation of VMs into computing nodes and determination of shares for each VM, maximizing total net utility. Shares parameters provide information to a virtualization scheduler 65 on how to distribute resources between contending VMs. Said database 63 contains several categories of information, comprising:

Category 1 Information: Information about the Target Servers:

-   -   These are the virtualized servers (e.g., VMware or Xen or         others) that host the VMs to be consolidated. Information for         each server type considered includes quantity of that server         type available and for each server type the following data:         -   1. Number of CPUs and speed of each CPU in MHz.         -   2. Memory size (e.g., in megabytes).         -   3. Storage interface configured (FC HBA or using Internet             Protocol (IP)).         -   4. IP Network interface configured.         -   5. Power utilization (how much power is used for amount of             CPU consumed). Power utilization can comprise a more complex             power model out of which the consolidation process can             derive relevant metrics.         -   6. Constraints and limitations (e.g., particular server can             only be assigned a maximum of 12 VMs, etc.).

Category 2 Information: Information about Source Applications:

-   -   These are the applications that are being moved from a physical         infrastructure into the new virtualized servers. For each         application, the following data is available:         -   1. CPU utilization over time.         -   2. Memory utilization over time.         -   3. Storage utilization over time.         -   4. Network utilization over time.         -   5. Constraints (e.g., one application can only be assigned             to a particular type of server).

Category 3 Information: Consolidation Process Specific Data:

-   -   This is the data that is required by the consolidation process:         -   1. Min and max for each source application. This can be             automatically derived as well from the Category 2             information above.         -   2. Utility of each application at min and max value of             resource. This may be input by an administrator via a             graphical user interface (GUI) provided by the consolidation             process.         -   3. Cost of power (e.g., how much does X watts cost in the             data center being considered for consolidation?).

The consolidation process comprises an analytical function for server consolidation by performing granular resource allocation during server consolidation, taking into account the utility of each VM application such that the overall utility of the system is maximized. The consolidation process employs virtualization and VM min, max, shares parameters for resource allocation analysis and enforcement. Employing min, max and shares parameters allows fine grained resource allocation to provide high utility workloads based on available physical server resources.

As is known to those skilled in the art, the aforementioned example architectures described above, according to the present invention, can be implemented in many ways, such as program instructions for execution by a processor, as software modules, microcode, as computer program product on computer readable media, as logic circuits, as application specific integrated circuits, as firmware, etc. The embodiments of the invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements. In a preferred embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc.

Furthermore, the embodiments of the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer, processing device, or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The medium can be electronic, magnetic, optical, or a semiconductor system (or apparatus or device). Examples of a computer-readable medium include, but are not limited to, a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a RAM, a read-only memory (ROM), a rigid magnetic disk, an optical disk, etc. Current examples of optical disks include compact disk-read-only memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.

I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be connected to the system either directly or through intervening controllers. Network adapters may also be connected to the system to enable the data processing system to become connected to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters. In the description above, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. For example, well-known equivalent components and elements may be substituted in place of those described herein, and similarly, well-known equivalent techniques may be substituted in place of the particular techniques disclosed. In other instances, well-known structures and techniques have not been shown in detail to avoid obscuring the understanding of this description.

The terms “computer program medium,” “computer usable medium,” “computer readable medium,” and “computer program product,” are used to generally refer to media such as main memory, secondary memory, removable storage drive, a hard disk installed in hard disk drive, and signals. These computer program products are means for providing software to the computer system. The computer readable medium allows the computer system to read data, instructions, messages or message packets, and other computer readable information, from the computer readable medium. The computer readable medium, for example, may include non-volatile memory, such as a floppy disk, ROM, flash memory, disk drive memory, a CD-ROM, and other permanent storage. It is useful, for example, for transporting information, such as data and computer instructions, between computer systems. Furthermore, the computer readable medium may comprise computer readable information in a transitory state medium such as a network link and/or a network interface, including a wired network or a wireless network that allow a computer to read such computer readable information. Computer programs (also called computer control logic) are stored in main memory and/or secondary memory. Computer programs may also be received via a communications interface. Such computer programs, when executed, enable the computer system to perform the features of the present invention as discussed herein. In particular, the computer programs, when executed, enable the processor or multi-core processor to perform the features of the computer system. Accordingly, such computer programs represent controllers of the computer system.

Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.

FIG. 7 shows a block diagram of example architecture of an embodiment of a system 100 for implementing an embodiment of the invention. The system 100 includes one or more client devices 101 connected to one or more server computing systems 130. A server 130 includes a bus 102 or other communication mechanisms for communicating information, and a processor (CPU) 104 coupled with the bus 102 for processing information. The server 130 also includes a main memory 106, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus 102 for storing information and instructions to be executed by the processor 104. The main memory 106 also may be used for storing temporary variables or other intermediate information during execution or instructions to be executed by the processor 104. The server computer system 130 further includes a read only memory (ROM) 108 or other static storage device coupled to the bus 102 for storing static information and instructions for the processor 104. A storage device 110, such as a magnetic disk or optical disk, is provided and coupled to the bus 102 for storing information and instructions. The bus 102 may contain, for example, thirty-two address lines for addressing video memory or main memory 106. The bus 102 can also include, for example, a 32-bit data bus for transferring data between and among the components, such as the CPU 104, the main memory 106, video memory and the storage 110. Alternatively, multiplex data/address lines may be used instead of separate data and address lines.

The server 130 may be coupled via the bus 102 to a display 112 for displaying information to a computer user. An input device 114, including alphanumeric and other keys, is coupled to the bus 102 for communicating information and command selections to the processor 104. Another type of user input device comprises cursor control 116, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to the processor 104 and for controlling cursor movement on the display 112.

According to one embodiment of the invention, the functions of the invention are performed by the server 130 in response to the processor 104 executing one or more sequences of one or more instructions contained in the main memory 106. Such instructions may be read into the main memory 106 from another computer-readable medium, such as the storage device 110. Execution of the sequences of instructions contained in the main memory 106 causes the processor 104 to perform the process steps described herein. One or more processors in a multi-processing arrangement may also be employed to execute the sequences of instructions contained in the main memory 106. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.

Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to the processor 104 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to the server 130 can receive the data on the telephone line and use an infrared transmitter to convert the data to an infrared signal. An infrared detector coupled to the bus 102 can receive the data carried in the infrared signal and place the data on the bus 102. The bus 102 carries the data to the main memory 106, from which the processor 104 retrieves and executes the instructions. The instructions received from the main memory 106 may optionally be stored on the storage device 110 either before or after execution by the processor 104.

The server 130 also includes a communication interface 118 coupled to the bus 102. The communication interface 118 provides a two-way data communication coupling to a network link 120 that is connected to the world wide packet data communication network now commonly referred to as the Internet 128. The Internet 128 uses electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on the network link 120 and through the communication interface 118, which carry the digital data to and from the server 130, are exemplary forms or carrier waves transporting the information.

In another embodiment of the server 130, interface 118 is connected to a network 122 via a communication link 120. For example, the communication interface 118 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line, which can comprise part of the network link 120. As another example, the communication interface 118 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface 118 sends and receives electrical electromagnetic or optical signals that carry digital data streams representing various types of information.

The network link 120 typically provides data communication through one or more networks to other data devices. For example, the network link 120 may provide a connection through the local network 122 to a host computer 124 or to data equipment operated by an Internet Service Provider (ISP) 126. The ISP 126 in turn provides data communication services through the Internet 128. The local network 122 and the Internet 128 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on the network link 120 and through the communication interface 118, which carry the digital data to and from the server 130, are exemplary forms or carrier waves transporting the information.

The server 130 can send/receive messages and data, including e-mail, program code, through the network, the network link 120 and the communication interface 118. Further, the communication interface 118 can comprise of a USB/Tuner and the network link 120 may be an antenna or cable for connecting the server 130 to a cable provider, satellite provider or other terrestrial transmission system for receiving messages, data and program code from another source.

The example versions of the invention described herein may be implemented as logical operations in a distributed processing system such as the system 100 including the servers 130. The logical operations of the present invention can be implemented as a sequence of steps executing in the server 130, and, as interconnected machine modules, within the system 100. The implementation is a matter of choice and can depend on performance of the system 100 implementing the invention. As such, the logical operations constituting said example versions of the invention are referred to for e.g. as operations, steps or modules.

Similar to a server 130 described above, a client device 101 can include a processor, memory, storage device, display, input device and communication interface (e.g., e-mail interface) for connecting the client device to the Internet 128, the ISP 126, or LAN 122, for communication with the servers 130.

The system 100 can further include computers (e.g., personal computers, computing nodes) 105 operating the same manner as client devices 101, wherein a user can utilize one or more computers 105 to manage data in the server 130.

Generally, the term “computer-readable medium”, as used herein, refers to any medium that participated in providing instructions to the processor 104 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as the storage device 110. Volatile media includes dynamic memory, such as the main memory 106. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise the bus 102. Transmission media can also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and not restrictive on the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other modifications may occur to those ordinarily skilled in the art. 

1. A method for consolidating a plurality of virtual machines and physical servers, the method comprising: assigning a virtual machine to a target physical server based on a plurality of virtualization parameters for maximizing utility of a plurality of virtual machines and physical servers, wherein assigning performs resource allocation for the virtual machine based on capabilities of the target physical server and a plurality of virtual machine resource requirements.
 2. The method of claim 1, wherein maximizing utility of the plurality of virtual machines and physical servers comprises a tradeoff between minimizing a number of physical servers utilized, minimizing power consumption, and maximizing utilization and performance.
 3. The method of claim 1, wherein the assigning further comprises: obtaining the plurality of virtualization parameters for the virtual machine, wherein the virtualization parameters comprise: a reservation parameter (min) representing a minimum resources required for a virtual machine, a limit parameter (max) representing a maximum resources allowable for a virtual machine, and a weight parameter (shares) representing a share of spare resources for a virtual machine.
 4. The method of claim 2, wherein the assigning further comprises: performing a power-performance tradeoff based on the plurality of virtualization parameters to determine an assignment of the virtual machine to the target physical server for maximizing utility of the plurality of virtual machines.
 5. The method of claim 4, wherein the assigning further comprises: discounting a power cost incurred, and considering an amount of resources on the target physical server to be allocated to the virtual machine.
 6. The method of claim 5, wherein the resource allocation further comprises: determining utility of the virtual machine based on at least one of: value and output the virtual machine can generate based on a plurality of resources allocated to the virtual machine.
 7. The method of claim 6, wherein the resource allocation further comprises: adjusting an amount of resources allocated to the virtual machine based on a plurality of available resources, a power consumption cost, and utility of the virtual machine.
 8. The method of claim 1, wherein consolidating further comprises: decommissioning a plurality of physical servers and deploying a plurality of virtual machines.
 9. A computer program product for consolidating a plurality of virtual machines and physical servers, the computer program product comprising a computer usable medium having computer readable program code embodied therewith, wherein the computer readable program when executed on the computer causes the computer to perform operations comprising: assigning a virtual machine to a target physical server based on a plurality of virtualization parameters for maximizing utility of the plurality of virtual machines and physical servers, wherein assigning performs resource allocation for the virtual machine based on capabilities of the target physical server and a plurality of virtual machine resource requirements.
 10. The computer program product of claim 9, further comprising: obtaining virtualization parameters for the virtual machine, the virtualization parameters comprising: a reservation parameter (min) representing a minimum resources required for the virtual machine, a limit parameter (max) representing a maximum resources allowable for the virtual machine, and a weight parameter (shares) representing a share of spare resources for the virtual machine.
 11. The computer program product of claim 10, wherein the assigning further comprises: performing power-performance tradeoff based on the virtualization parameters to determine an assignment of the virtual machine to a target physical server while maximizing the overall utility of the plurality of virtual machines.
 12. The computer program product of claim 11, wherein the assigning further comprises: maximizing the overall utility of the plurality of virtual machines discounting the power costs incurred, considering an amount of resource on the target physical server to be allocated to the virtual machine.
 13. The computer program product of claim 12, wherein the resource allocation further comprises: determining utility of the virtual machine based on at least one of: value and output the virtual machine can generate given the resources allocated to the virtual machine.
 14. The computer program product of claim 13, wherein the resource allocation further comprises: adjusting the amount of resources allocated to the virtual machine based on available resources, power consumption cost, and virtual machine utility.
 15. The computer program product of claim 14, further comprising decommissioning physical servers and deploying virtual machines.
 16. A system for consolidating a plurality of virtual machines and physical servers, the system comprising: a consolidation module comprising an assignment module configured for assigning a virtual machine to a target physical server based on a plurality of virtualization parameters for maximizing utility of a plurality of virtual machines and physical servers, and an allocation module configured for resource allocation for the virtual machine based on capabilities of the target physical server and a plurality of virtual machine resource requirements, by performing a tradeoff between minimizing number of physical servers utilized, minimizing power consumption, to maximize at least one of system utilization and performance.
 17. The system of claim 16, wherein: the assignment module is further configured for assigning the virtual machine to a target physical server by obtaining virtualization parameters for the virtual machine, and performing power-performance tradeoff based on the virtualization parameters to determine an assignment of the virtual machine to a target physical server while maximizing the overall utility of the virtual machines; the virtualization parameters comprise: a reservation parameter (min) representing a minimum resources required for the virtual machine, a limit parameter (max) representing a maximum resources allowable for the virtual machine, and a weight parameter (shares) representing a share of spare resources for the virtual machine.
 18. The system of claim 17, further wherein the assignment module is further configured for: assigning the virtual machine to a target physical server by maximizing the overall utility of the virtual machines discounting the power costs incurred, considering an amount of resource on the target physical server to be allocated to the virtual machine.
 19. The system of claim 18, wherein the allocation module is further configured for performing resource allocation for the virtual machine by determining utility of the virtual machine based on at least one of: value and output the virtual machine can generate given the resources allocated to the virtual machine.
 20. The system of claim 19, wherein the allocation module is further configured for performing resource allocation for the virtual machine by adjusting the amount of resources allocated to the virtual machine based on available resources, power consumption cost, and virtual machine utility. 